Provisioning data volumes for containers running in virtual machines in which storage for the virtual machines are backed by heterogeneous storage devices

ABSTRACT

A computer system has a virtualization software that supports execution of a virtual machine in which a container is run. A method of provisioning first and second data volumes for the container, wherein the first data volume is backed by storage device of a first type and the second data volume is backed by storage device of a second type, includes monitoring a designated virtual socket, detecting, based on monitoring, a first request from a plug-in of the container to create a first data volume having first storage requirements, upon detecting the first request, communicating the request to the virtualization software to create the first data volume, detecting, based on monitoring, a second request from a plug-in of the container to create a second data volume having second storage requirements, and upon detecting the second request, communicating the request to the virtualization software to create the second data volume.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of priority from U.S. Provisional Patent Application No. 62/343,780, filed May 31, 2016, which is incorporated by reference herein.

BACKGROUND

Increasingly, decisions to provision resources and manage resources are made by application logic, e.g., containers, running within virtual machines (VMs), and they typically require a self-serve-programmatic model for provisioning and management. Some frameworks can choose to create an instance of a container image and attach persistent storage (e.g., data volumes) to the container image, all within the VM.

However, there exist challenges when trying to meet the need for a self-serve-programmatic model. Some existing management stacks require manual steps, including opening up a user interface (UI) and directing the provisioning of data volumes through the UI. Other existing management stacks require invoking of a remote application programming interface (API) to a control plane for provisioning data volumes. This latter technique typically also requires per VM configuration.

SUMMARY

One or more embodiments provide a control plane for data volume management that can be invoked within a container that is spun up within a VM. One example of a data volume is a virtual disk. More generally, a “data volume” is a place where the container can store data persistently. The control plane is configured as a daemon or other service that is running in the user space of a hypervisor that is supporting the execution of the VM and listens in on a virtual socket provisioned within the VM.

Advantages of employing the control plane within the hypervisor, according to embodiments, are as follows. First, it does not require human intervention to carry out the data volume provisioning requested by the application administrator. Second, the control plane is local to the VM and does not require any additional configuration beyond the installation of the data volume plug-in software in the VM.

In one embodiment, to protect against untrusted plug-ins from sending control operations to a control plane within the hypervisor, the control plane requires control operations passed thereto to originate from software running in the root mode. As a result, only those plug-ins that are trusted software (e.g., signed with proper cryptographic keys) will be able to send control operations successfully to the control plane. For example, control operations sent to the control plane via third party plug-ins, which would be running in non-root mode, will be not be accepted by the control plane.

A method of provisioning first and second data volumes for the container, wherein the first data volume is backed by storage device of a first type and the second data volume is backed by storage device of a second type, includes the steps of monitoring a designated virtual socket, detecting, based on the monitoring, a first request from a plug-in of the container to create a first data volume having first storage requirements, upon detecting the first request, communicating the request to the virtualization software to cause the virtualization software to create the first data volume, detecting, based on the monitoring, a second request from a plug-in of the container to create a second data volume having second storage requirements, and upon detecting the second request, communicating the request to the virtualization software to cause the virtualization software to create the second data volume.

Further embodiments include, without limitation, a non-transitory computer-readable medium that includes instructions that enable a processor to implement one or more aspects of the above method as well as a computer system having a processor, memory, and other components that are configured to implement one or more aspects of the above method.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a virtualized computing environment in which embodiment may be practiced.

FIG. 2A is a conceptual diagram that illustrates how plug-ins enable data volume provisioning from different types of storage according to the related art.

FIG. 2B is a conceptual diagram that illustrates how a single plug-in enables data volume provisioning from different types of storage according to embodiments.

FIG. 2C is an example of a table used in selecting the storage hardware according to embodiments.

FIG. 3 is a flow diagram of a method of creating a data volume according to embodiments.

FIG. 4 is a flow diagram of a method of mapping a data volume to a namespace according to embodiments.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a virtualized computing environment in which embodiments may be practiced. The virtualized computing environment of FIG. 1 includes a cluster of host computer systems 100-1 to 100-N, where N is 2 or more. Alternatively, embodiments may be practiced in a virtualized computing environment that includes only a single host computer system. Host computer system 100-1 has a hardware platform 120-1 that includes one or more central processing units (CPUs) 121, system memory 122 (typically volatile dynamic random access memory), one or more network interface controllers (NICs) 123, and one or more host bus adapters (HBAs) 124. Each of the other host computer systems 100, including host computer system 100-N which has a hardware platform 120-N, includes the same (or similar) hardware components as hardware platform 120-1. In addition, a hypervisor is installed in each of host computer systems 100 as system software. Hypervisor 110-1 supports the execution space of virtual machines (VMs) 130-1 and hypervisor 110-N supports the execution space of VMs 130-M. Hereinafter, VMs will be generally referred to as VM 130 or VMs 130 and the hypervisor supporting the VMs 130 will be generally referred to as hypervisor 110.

As further illustrated in FIG. 1, a container 131 runs inside VM 130-1 on top of an operating system (OS) 140 of VM 130-1. One example of container 131 is a Docker® container that runs on top of a Linux® operating system. Typically, container 131 includes a management layer (known as a container engine) on top of OS 140 and one or more applications deployed therein to run on top of the management layer.

In FIG. 1, a plug-in 133 is also illustrated. Plug-in 133, which is implemented as part of the plug-in framework of the container (e.g., as part of Docker® plug-in framework for Docker® containers), is configured to communicate with hypervisor 110-1 over a virtual socket provisioned by hypervisor 110-1 as part of a virtual hardware platform for VM 130-1. The virtual socket is also referred to as a back channel, and enables VM 130-1 to communicate with hypervisor 110-1. In one embodiment, the virtual socket is implemented as shared memory, such as with virtual machine control interface (VMCI) employed in virtualization products available from VMware, Inc. of Palo Alto, Calif., and is accessed through VMCI ports. More specifically, daemon 111 runs in a user space of hypervisor 110-1 to listen in on this virtual socket and, in the embodiments, passes on control operations received through this virtual socket to hypervisor 110-1 for execution using standard APIs. Examples of these standard APIs include creating a data volume, deleting a data volume, attaching a data volume, and detaching a data volume. Accordingly, operations to create, delete, attach, or detach a data volume can be instigated within container 131 and such control operations are “plumbed” to plug-in 133 that forwards those control operations over the virtual socket to daemon 111, which calls the standard APIs to perform control operations on the data volume.

A virtual machine management server (VMMS) 160 manages VMs across host computers systems 100. The execution of the VMs is supported by the hypervisors of the respective host computer systems 100. The standard APIs exposed by hypervisor 110 for creating, deleting, attaching, and detaching a data volume are made accessible through a user interface of VMMS 160 so that control operations for data volumes of VMs (e.g., virtual disks) can be instigated by a VM administrator.

The data volumes for the container or the VMs are stored in storage system 150. In the embodiment illustrated in FIG. 1, storage system 150 is a shared storage system, which is accessible from host computer systems 100 through their HBAs 124. In another embodiment, storage system 150 may be network-attached storage (NAS) or virtual storage area network (SAN), which is accessible from host computer systems 100 over a network through their NICs 123.

According to embodiments, the data volume control plane is implemented in hypervisor 110 through daemon 111 which is listening in on the virtual socket through which plug-in 133 forwards data volume control operations. As data volume control operations are passed down from container 131 to plug-in 133 and forwarded onto the virtual socket, daemon 111, upon detection of the data volume control operation, invokes the standard APIs exposed by hypervisor 110 for provisioning data volumes. As a way to protect against untrusted applications or plug-ins from gaining access to the data volume control plane, any application or plug-in not running in root mode are blocked from gaining access to the data volume control plane. This is implemented by daemon 111 listening in on a privileged virtual socket, i.e., the virtual socket that is accessed through a privileged VMCI port. As such, any control operations forwarded onto a non-privileged virtual socket will be ignored by daemon 111. Accordingly, in the embodiments, plug-in 133 is implemented as a secure module that runs in root mode. In order to preserve its image and to protect it against tampering, the executable code of this secure module is signed with cryptographic keys of a trusted entity.

In addition, the VM administrator who is managing the virtualized computing environment the infrastructure can set bounds on data volume provisioning. The application administrator is free to perform data volume control operations so long as they are within these bounds. The bounds include quotas (capacity), what kind of volumes, and how many volumes. Roles are also defined by the VM administrator. The roles specify which VMs may create or delete, which VMs may read or write. In addition, the VM administrator is given the ability to view and inspect the run time of the VMs (which data volumes were created by whom, who is consuming them, which volumes are unused, how much data was written, etc.)

FIG. 2A is a conceptual diagram that illustrates how plug-ins enable data volume provisioning from different types of storage according to the related art. In the related art, different data volume plug-ins are written for storage hardware of different storage vendors and for different types of storage hardware. Accordingly, when a container is deployed within a VM, the data volume plug-in for the container has to be matched to the actual storage hardware that is providing storage for the container. FIG. 2A shows that container 131 relies on plug-in A 33A for data volume control operations performed on storage array 200A, plug-in B 33B for data volume control operations performed on flash 200B, plug-in C 33C for data volume control operations performed on NAS 200C, and plug-in D 33D for data volume control operations performed on custom storage 200D (e.g., storage hardware commercially available from a particular storage vendor). Potentially, there are multiple storage vendors, each providing different storage hardware associated with different plug-ins, and other types of storage in addition to the examples given in FIG. 2A. However, only four are shown for purpose of illustration.

By contrast, as shown in the conceptual diagram of FIG. 2B, according to embodiments, a single plug-in, e.g., plug-in 133, enables data volume provisioning from different types of storage. The different types of storage may be physical or virtual. Examples of different types of physical storage devices are magnetic disk-based storage devices, flash memory devices, and hybrid devices that incorporate both magnetic disk-based storage and flash memory. Examples of different types of virtual storage devices are virtual SAN devices, which are described in U.S. patent application Ser. No. 14/010,293, filed Aug. 26, 2013, the entire contents of which are incorporated by reference herein, and virtual volumes, which are described in U.S. patent application Ser. No. 14/273,420, filed May 8, 2014, the entire contents of which are incorporated by reference herein. In addition, physical storage devices may differ as a result of the communication protocol they employ. Two such examples are SAN devices and NAS devices. Finally, storage devices (whether physical or virtual) may differ because the storage vendor is different. Within hypervisor 110, the different types of storage, whether from the same storage vendor or different storage vendors, and whether physical or virtual, are already virtualized (and if not already virtualized, can be virtualized within hypervisor 110), and embodiments leverage this knowledge to be able to consume each of the different types of storage from different storage vendors with a single plug-in. In contrast to the related art, during deployment of a container within a VM, there is no need for matching of the plug-in to the actual storage hardware that is providing storage for the container. As a result, the administrator of containers no longer needs to be aware of all the storage hardware choices and no longer needs to match the data volume plug-in to the storage hardware.

In one embodiment, hypervisor 110 maintains a file that tracks the capacity and the capabilities of different types of storage that hypervisor 110 has already virtualized. One example of this storage capability tracking file contains a table that is illustrated in FIG. 2C. When hypervisor 110 receives APIs corresponding to a data volume create command with an expressed policy, hypervisor 110 examines the storage capability tracking file to select the storage hardware that best meets the storage requirements of the expressed policy and provisions a data volume from this storage hardware.

FIG. 3 is a flow diagram of a method of creating a data volume according to embodiments. The method illustrated in FIG. 3 is carried out by container 131, plug-in 133, and daemon 111. When the application administrator desires to create a data volume for container 131, the application administrator enters command line instructions for creating the data volume at step 311, e.g., “create docker volume, driver=vmdk, name=radio2016, size=10 GB, policy” where policy represents the storage requirements for the data volume that the application administrator enters, such as “thin_provisioning=yes; 8000<TOPS<10000; max_latency=5 msec.” In response to the command line instruction entered at step 311, container 131 searches for a plug-in of the driver indicated in the command, in this example, vmdk, and sends the create data volume command to the plug-in (step 312).

At step 321, the plug-in, e.g., plug-in 133, upon receipt of the create data volume command from container 131, forwards the create data volume command to daemon 111 through a virtual socket. In particular, plug-in 133 invokes a virtual socket API to forward the create data volume command to the virtual socket through a privileged VMCI port (e.g., a VMCI port that has been pre-designated as a privileged port).

Daemon 111 runs as a background process in the user space of hypervisor 110, and listens in on (monitors) the privileged virtual socket for new requests at step 331. Upon detecting a create data volume request that includes the expressed policy, daemon 111 at step 332 invokes the standard APIs for (1) creating a data volume for the virtual machine that is hosting container 131, and (2) reconfiguring the virtual machine to add the data volume (i.e., updating the virtual machine configuration file to include an identifier for the newly provisioned data volume). When invoking the standard APIs, daemon 111 sets the parameters of the APIs to reflect the storage requirements that are expressed in the policy. In response to the APIs invoked at step 332, hypervisor 110 provisions a new data volume in the appropriate storage hardware, and the newly provisioned data volume becomes attached to the virtual machine (i.e., the newly provisioned data volume is enumerated as one of the devices of the virtual machine). In addition, daemon 111 maintains a metadata file in memory 122 and persisted in storage system 150, to track the association of new data volumes and the virtual machines for which the new data volumes have been created. According to embodiments, the application administrator merely needs to request a data volume of certain size and specify a policy that reflects the desired storage requirements, and hypervisor 110 will, based on the size and storage requirements, select a storage hardware of a particular storage vendor, from which a data volume that meets these requirements can be provisioned, and then provision the data volume from the selected storage hardware.

At step 322, plug-in 133 formats the data volume with a file system. A file system specified by the application administrator in the command line instructions may be used in formatting the data volume. If no such file system is specified, a default file system is used.

After the data volume has been formatted with the file system at step 322, the control returns to daemon 111, at which time daemon invokes the standard API for reconfiguring the virtual machine to detach the data volume (i.e., updating the virtual machine configuration file to remove the identifier for the newly provisioned data volume). In response to the API invoked at step 333, the newly provisioned data volume becomes detached from the virtual machine (i.e., the newly provisioned data volume is no longer enumerated as one of the devices of the virtual machine).

FIG. 4 is a flow diagram of a method of mapping a data volume to a namespace according to embodiments. The method illustrated in FIG. 4 is carried out by container 131, plug-in 133, and daemon 111, and in response to a container run command. When the application administrator desires to map a data volume to a namespace for container 131, the application administrator enters command line instructions to run the container at step 411, e.g., “docker run, radio2016:/busybox.” When this particular command line instruction is executed within container 131, container 131 is spun up using data volume, radio2016, mapped to the namespace/busybox. Also, in response to the command line instruction entered at step 411, container 131 locates the plug-in corresponding to the data volume indicated in the command, in this example, radio2016, and sends a get data volume command to the plug-in (step 412).

At step 421, the plug-in, e.g., plug-in 133, upon receipt of the get data volume command from container 131, forwards the get data volume command to daemon 111 through a virtual socket. In particular, plug-in 133 invokes a virtual socket API to forward the get data volume command to the virtual socket through the privileged VMCI port.

Daemon 111 listens in on (monitors) the privileged virtual socket for new requests at step 431. Upon detecting a get data volume request, daemon 111 at step 432 checks the metadata file to see if the data volume exists. If no such data volume exists, daemon 111 returns an error at step 433. If the data volume exists, daemon 111 at step 434 invokes the standard APIs for reconfiguring the virtual machine to add the data volume (i.e., updating the virtual machine configuration file to include an identifier for the data volume). In response to the APIs invoked at step 434, the data volume becomes attached to the virtual machine (i.e., the data volume is enumerated as one of the devices of the virtual machine).

In response to the virtual socket API invoked at step 421, plug-in 133 at step 422 receives a device ID corresponding to the data volume from daemon 111, maps the device ID to the data volume, and mounts the file system of the data volume into the namespace used by container 131 so that the data volume can be mapped to a folder accessible by container 131, e.g., so that the volume, radio2016, can be mapped to the /busybox folder.

In the example given above, a container that instigated the creation of a data volume may be the same or different from a container that is run using that data volume. In addition, a container that instigated the creation of a data volume may be running in a first virtual machine and a container that is run using that data volume may be running in a second virtual machine. The first and second virtual machines may be executed in the same or different host computer systems so long as the host computer systems are accessing the same storage system in which the data volume is provisioned.

Certain embodiments as described above involve a hardware abstraction layer on top of a host computer. The hardware abstraction layer allows multiple contexts or emulated computing instances to share the hardware resource. In one embodiment, these emulated computing instances are isolated from each other, each having at least a user application running therein. The hardware abstraction layer thus provides benefits of resource isolation and allocation among the emulated computing instances. In the foregoing embodiments, emulated machines are used as an example for the emulated computing instances and hypervisors as an example for the hardware abstraction layer. As described above, each emulated machine includes a guest operating system in which at least one application runs.

The various embodiments described herein may employ various computer-implemented operations involving data stored in computer systems. For example, these operations may require physical manipulation of physical quantities usually, though not necessarily, these quantities may take the form of electrical or magnetic signals, where they or representations of them are capable of being stored, transferred, combined, compared, or otherwise manipulated. Further, such manipulations are often referred to in terms, such as producing, identifying, determining, or comparing. Any operations described herein that form part of one or more embodiments of the invention may be useful machine operations. In addition, one or more embodiments of the invention also relate to a device or an apparatus for performing these operations. The apparatus may be specially constructed for specific required purposes, or it may be a general purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general purpose machines may be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.

The various embodiments described herein may be practiced with other computer system configurations including hand-held devices, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.

One or more embodiments of the present invention may be implemented as one or more computer programs or as one or more computer program modules embodied in one or more computer readable media. The term computer readable medium refers to any data storage device that can store data which can thereafter be input to a computer system computer readable media may be based on any existing or subsequently developed technology for embodying computer programs in a manner that enables them to be read by a computer. Examples of a computer readable medium include a hard drive, network attached storage (NAS), read-only memory, random-access memory (e.g., a flash memory device), a CD (Compact Discs) CD-ROM, a CD-R, or a CD-RW, a DVD (Digital Versatile Disc), a magnetic tape, and other optical and non-optical data storage devices. The computer readable medium can also be distributed over a network coupled computer system so that the computer readable code is stored and executed in a distributed fashion.

Although one or more embodiments of the present invention have been described in some detail for clarity of understanding, it will be apparent that certain changes and modifications may be made within the scope of the claims. Accordingly, the described embodiments are to be considered as illustrative and not restrictive, and the scope of the claims is not to be limited to details given herein, but may be modified within the scope and equivalents of the claims. In the claims, elements and/or steps do not imply any particular order of operation, unless explicitly stated in the claims.

Plural instances may be provided for components, operations or structures described herein as a single instance. Finally, boundaries between various components, operations and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within the scope of the invention(s). In general, structures and functionality presented as separate components in exemplary configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements may fall within the scope of the appended claims. 

What is claimed is:
 1. In a computer system having a virtualization software supporting execution of a virtual machine in which a container is run, a method of provisioning first and second data volumes for the container, comprising: monitoring a designated virtual socket; based on said monitoring, detecting a first request from a plug-in of the container to create a first data volume having first storage requirements; upon detecting the first request, communicating the request to the virtualization software to cause the virtualization software to create the first data volume; based on said monitoring, detecting a second request from a plug-in of the container to create a second data volume having second storage requirements; and upon detecting the second request, communicating the request to the virtualization software to cause the virtualization software to create the second data volume, wherein the first data volume is backed by storage device of a first type and the second data volume is backed by storage device of a second type.
 2. The method of claim 1, wherein the storage device of the first type and the storage device of the second type have different storage capabilities.
 3. The method of claim 2, wherein the storage device of the first type have a maximum IOPS that is less than that of the storage device of the second type.
 4. The method of claim 2, wherein the storage device of the first type is a magnetic disk and the storage device of the second type is flash memory.
 5. The method of claim 1, wherein the storage device of the first type and the storage device of the second type are manufactured by different storage vendors.
 6. The method of claim 1, further comprising: based on said monitoring, detecting a request from the plug-in of the container to map a data volume to a namespace used by the container; upon detecting the request to map, determining if the data volume has been created; if the data volume has been created, mounting a file system for the data volume into the namespace used by the container so as to map the data volume to a folder accessible by the container; and if the data volume has not been created, returning an error.
 7. The method of claim 6, wherein the data volume that the plug-in of the container is requesting to map is one of the first and second data volumes.
 8. The method of claim 6, wherein the data volume that the plug-in of the container is requesting to map is different from the first and second data volumes.
 9. The method of claim 8, wherein the data volume that the plug-in of the container is requesting to map is a data volume that a plug-in of a different container requested to create.
 10. A non-transitory computer readable medium comprising instructions to be executed in a computer system having a virtualization software supporting execution of a virtual machine in which a container is run, wherein the instructions when executed cause the computer system to carry out a method of provisioning first and second data volumes for the container, said method comprising: monitoring a designated virtual socket; based on said monitoring, detecting a first request from a plug-in of the container to create a first data volume having first storage requirements; upon detecting the first request, communicating the request to the virtualization software to cause the virtualization software to create the first data volume; based on said monitoring, detecting a second request from a plug-in of the container to create a second data volume having second storage requirements; and upon detecting the second request, communicating the request to the virtualization software to cause the virtualization software to create the second data volume, wherein the first data volume is backed by storage device of a first type and the second data volume is backed by storage device of a second type.
 11. The non-transitory computer readable medium of claim 10, wherein the storage device of the first type and the storage device of the second type have different storage capabilities.
 12. The non-transitory computer readable medium of claim 11, wherein the storage device of the first type have a maximum IOPS that is less than that of the storage device of the second type.
 13. The non-transitory computer readable medium of claim 11, wherein the storage device of the first type is a magnetic disk and the storage device of the second type is flash memory.
 14. The non-transitory computer readable medium of claim 10, wherein the storage device of the first type and the storage device of the second type are manufactured by different storage vendors.
 15. The non-transitory computer readable medium of claim 10, wherein the method further comprises: based on said monitoring, detecting a request from the plug-in of the container to map a data volume to a namespace used by the container; upon detecting the request to map, determining if the data volume has been created; if the data volume has been created, mounting a file system for the data volume into the namespace used by the container so as to map the data volume to a folder accessible by the container; and if the data volume has not been created, returning an error.
 16. The non-transitory computer readable medium of claim 15, wherein the data volume that the plug-in of the container is requesting to map is one of the first and second data volumes.
 17. The non-transitory computer readable medium of claim 15, wherein the data volume that the plug-in of the container is requesting to map is different from one of the first and second data volumes.
 18. The non-transitory computer readable medium of claim 17, wherein the data volume that the plug-in of the container is requesting to map is a data volume that a plug-in of a different container requested to create.
 19. A computer system having a first host computer system including a first virtualization software supporting execution of a first virtual machine in which a first container is run, and a second host computer system including a second virtualization software supporting execution of a second virtual machine in which a second container is run, wherein the first virtualization software has a background process running therein to perform the steps of: monitoring a designated virtual socket; based on said monitoring, detecting a first request from a plug-in of the container to create a first data volume having first storage requirements; upon detecting the first request, communicating the request to the virtualization software to cause the virtualization software to create the first data volume; based on said monitoring, detecting a second request from a plug-in of the container to create a second data volume having second storage requirements; and upon detecting the second request, communicating the request to the virtualization software to cause the virtualization software to create the second data volume, wherein the first data volume is backed by storage device of a first type and the second data volume is backed by storage device of a second type.
 20. The computer system of claim 19, wherein the storage device of the first type is one of a SAN device, a virtual SAN device, a virtual volume, and a NAS device, and the storage device of the second type is a different one of the SAN device, the virtual SAN device, the virtual volume, and the NAS device. 